System and method for validating channel transmission

ABSTRACT

A system for validating communications between a plurality of processors is disclosed. The system includes a plurality of loop back paths, and each of the loop back paths is coupled to a corresponding one of the plurality of processors. In addition, each loop back path is configured to attenuate one of a plurality of signals transmitted from each of the corresponding ones of the plurality of processors so as to generate a plurality of loop back signals. A plurality of signal transmission paths are configured to carry a corresponding one of the plurality of signals from one of the plurality of processors to another of the plurality of processors, and a plurality of comparators compare the plurality of loop back signals to the plurality of transmission signals so as to enable the validity of each of the plurality of signals to be assessed.

RELATED APPLICATIONS

This application is a continuation application of co-pending applicationSer. No. 11/242,401 filed Oct. 3, 2005, which is a continuationapplication of application Ser. No. 10/848,542 filed May 17, 2004, whichis a continuation of Ser. No. 10/226,454, filed Aug. 22, 2002, which isa continuation application of application Ser. No. 09/467,669 filed onDec. 18, 1999, which application claimed benefit of prior filedprovisional Application No. 60/112,832 filed on Dec. 18, 1998. Theentire contents of each of these applications is hereby incorporated byreference herein for all purposes.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The field of this invention related to computerized control systems forgathering sensor data from field units and triggering alarms or takingother actions based on the sensor data with respect to such controlelements. More particularly this invention relates to multiple processorcontrol units which are synchronized and evaluate sensor data for validdata.

2. Related Art

Many multiple processor control systems are available in the relatedart. These include systems as typified by U.S. Pat. No. 5,455,914 toHashemi, et al. includes a multiple module processor which is controlledfrom a central computer station.

U.S. Pat. No. 4,616,312 to Uebel, describes a two-out-of-three selectingfacility in a three-computer system for a Triple Redundant ComputerSystem which is especially suitable for use with microprocessors havinga large number of outputs. The computers of the three computer systemhandle the same processor information in parallel, but exchange theirresults in an asynchronous manner and compares them.

U.S. Pat. No. 4,627,055 to Mori, et al. describes a decentralizedprocessing method and system having a plurality of subsystems of thesame type which are connected to one another. Each subsystem has adiagnostic mean for diagnosis of failure in the other subsystems andfunctions to take suitable counter-measures.

U.S. Pat. No. 5,239,641 to Horst, for a method and a apparatus forsynchronizing a plurality of processors. Each processor runs off its ownindependent clock, indicates the occurrence of a predescribed processorevent on one line and receives signals on another line for initiating aprocessor wait state.

However, the I/O architecture of the present invention is fundamentallydifferent from prior systems, in that the prior systems rely onintelligent I/O modules, with one microprocessor per leg per module,while the present invention relies on centralized I/O logic, with onemicroprocessor per leg, controlling all the I/O modules. A degree oflocal intelligence on each I/O module is implemented through gate arraylogic, acting primarily as a slave to the main processor. Thisarchitecture reduces the component cost and eliminates the significantsize of such system which are usually housed in a central location. Aunique synchronization system keeps the local clocks in synchronization.

The present invention provides a system which is intended to operateadjacent the equipment being controlled.

SUMMARY OF THE INVENTION

The control system of the present invention comprises a fault tolerantcontroller, control system platform or computer system having a triplemodular redundant (TMR) architecture. The controller consist of threeidentical channels, except for the power modules which aredual-redundant. Each channel independently executes the applicationprogram in parallel with the other two channels. A voting system withvoting mechanisms which qualify and verify all digital inputs andoutputs from the field; analog inputs are subject to a mid-valueselection process.

Each channel is isolated from the others, no single-point failure in anychannel can pass to another. If a hardware failure occurs in onechannel, the faulty channel is overridden by the other channels. Repairconsists of removing and replacing the failed module in the faultychannel while the controller is online and without process interruption.

The controller of the present invention features triplicated mainprocessor modules (MP), input/output modules (I/O) and optionally one ortwo Local Communications modules (LCM). Each I/O module houses thecircuitry for three independent channels. Each channel on the inputmodules reads the process data and passes that information to itsrespective MP. The three MP communicate with each other using ahigh-speed bus called Channel 11

The system is a scan based system and once per scan, the MP modulesynchronizes and communicate with the neighboring MPs over the Channel11. The Channel 11 forwards copies of all analog and digital input datato each MP, and compares output-data from each MP. The MPs vote theinput data, execute the application program and send outputs generatedby the application program to the output modules. In addition, thecontroller votes the output data on the output modules as close to thefield as possible to detect and compensate for any errors that couldoccur between the Channel 11 voting and the final output driven to thefield. For each I/O module, the controller can support an optionhot-spare module. If present, the hot-spare takes control if a fault isdetected on the primary module during operation. The hot-spare positionis also used for the online-hot repair of a faulty I/O module.

The MP modules each control a separate channel and operates in parallelwith the other two MPs. A dedicated I/O control processor on each MPmanages the data exchanged between the MP and the I/O modules. Atriplicated I/O bus, located on the base plates, extends from one columnof I/O modules to another column of I/O modules using I/O bus cables. Inthis way the system can be expanded. Each MP poles the appropriatechannel of the I/O bus and the I/O bus transmits new input data to theMP on the polling channel. The input data is assembled into a table inthe MP and is stored in memory for use in the voting process.

Each input table in each M is transferred to its neighboring MP over theChannel 11. After this transfer, voting takes place. The Channel 11 usesa programmable device with a direct memory access to synchronize,transmit, and compare data among the three MPs.

If a disagreement occurs, the signal value found in two of three tablesprevails, and the third table is corrected accordingly. Each WPmaintains data about necessary correction in local memory. Any disparityis flagged and used at the end of the scan by built-in fault analyzerroutines to determine whether a fault exists on a particular module.

The MPs send corrected data to the application program and then executesthe application program in parallel with the neighboring MP andgenerates a table of output values that are based on the table of inputvalues according to user-defined rules. The I/O control processor oneach MP manages the transmission of output data to the output modules bymeans of the I/O bus.

Using the table out output values, the I/O control processor generatessmaller tables, each corresponding to an individual output module. Eachsmall table is transmitted to the appropriate channel of thecorresponding output module over the I/O bus. For example, MP Atransmits the appropriate table to channel A of each output module overthe I/O bus A. The transmittal of output data has priority over theroutine scanning of all I/O modules.

Each MP provides a 16-megabyte DRAM for the user-written applicationprogram, sequence-of-events (SOE) tracking, and I/O data, diagnosticsand communication buffers. The application program is stored in flashEPROM and loaded into DRAM for execution. The MPs receive power fromredundant 24 VDC power sources. In the event of an external powerfailure, all critical retentive data is stored in NVRAM. A failure ofone power source does not affect controller performance. If thecontroller loses power, the application program and all critical dataare retained.

In addition, each MP can provide direct development and monitoringcomputer support and Modbus communication Each MP provides one (IEEE802.3 Ethernet) Development System computer port for downloading theapplication program to the Trident controller and uploading diagnosticinformation, one Modbus RE-232/RS485 serial port which acts as a slavewhile an external host computer is the master. Typically, a distributedcontrol system (DCS) monitors and optionally updates the controller datadirectly through an MP.

The triplicated I/O bus is carried baseplate-to-baseplate usingInterconnect Assemblies, extender modules, and I/O bus cables. Theredundant logic power distribution system is carried using InterconnectAssemblies and Extender modules.

The Channel 11, which is local to the MP baseplate, consists of threeindependent, serial links operating at 25 Mbaud. It synchronizes the MPsat the beginning of a scan. Then each MP sends its data to its upstreamand downstream neighbors. The Channel 11 takes the following actions:transfers input, diagnostic and communication data, compares data andflags disagreements for the previous scan's output data and applicationprogram memory. A single transmitter is used to send data to both theupstream and downstream MPs. This ensures that the same data is receivedby the upstream processor and the downstream processor.

Field signal distribution is local to each I/O baseplate. Each I/Omodule transfers signals to or from the field through its associatedbaseplate assembly. The two I/O module slots on the baseplate tietogether as one logical slot. A first position holds the active I/Omodule and the second position holds the hot-spare I/O module. Eachfield connection on the baseplate extends to both active and hot-spareI/O modules. Therefore, both the active module and the hot-spare modulereceive the same information from the field termination wiring.

The 2 Mbaud triplicated I/O bus transfers data between the I/O modulesand the MP. The I/O bus is carried along the DIN mounting rail and canbe extended to multiple DIN rails. Each channel of the I/O bus runsbetween one MP and the corresponding channel on the I/O module. The I/Obus extends between DIN rails using a set of three I/O bus cables.

Logic power for the module on each DIN mounting rail draws power fromthe power rails through redundant DC-DC power converters. Each channelis powered independently from these redundant power sources.

The controller of the present invention incorporates integral onlinediagnostics. These diagnostics and specialized fault monitoringcircuitry are able to detect and alarm all single fault and mostmultiple fault conditions. The circuitry includes but is not necessarilylimited to I/O loop-back, watch-dog timers, and loss-of power sensors.Using the alarm information, the user is able to tailor the response ofthe system to the specific fault sequence and operating priorities ofthe application.

Each module can activate the system integrity alarm, which consists ofnormally closed (NC) relay contacts on each MP Module. Any failurecondition, including loss or brown-out of system power, activates thealarm to summon plant maintenance personnel.

The front panel of each module provides light-emitting-diode (LED)indicators that show the status of the module or the external systems towhich it may be connected, PASS, FAULT, and ACTIVE are commonindicators. Other indicators are module—specific. A common modulehousing structure which accepts all circuit boards for the variousmodules

Normal maintenance consists of replacing plug-in modules. A lightedFAULT indicator shows that the module has detected a fault and must bereplaced.

All internal diagnostic and alarm status data is available for remotelogging and report generation. Reporting is done through a local orremote host computer.

Additional special features include fault testing of channels through aloop-back through the base plate to ensure that the transmitting moduleis accurately transmitting data, and status information.

The MP modules running in parallel rendezvous each scan to vote, and runthe application program. At each rendezvous the modules are timesynchronized by the adjustment of their time clocks by a specificamount. Dependent on the disparity between time clocks either a positiveor a negative adjustment is made to those clocks out of synchronization.

A System Executive runs the application program developed by a controlengineer for a specific industrial site which is downloaded from adevelopment PC. A System Input/Output Executive facilitatescommunication with the input/output modules and the System Executive.Both the System Executive and the System Input/Output Executive areresident on each MP processor modules.

Each processor module MP consists of two semi-independent designs, theprocessor section and the input/output section. The processor section isdedicated to the System Executive and associated firmware, theinput/output section is dedicated to System Input/Output Executive andassociated firmware. There are three processor modules in a system.

The three processor modules communicate with each other via aninter-processor bus called the Channel 11. The Channel 11 is a highspeed fault tolerant communication path between the processors and isused primarily used for voting data. The three processor modules aretime synchronized with each other by a fault tolerant subsystem calledthe synchronization system. Each processor module contains two portsthat can be used for interface with a development computer system or asa slave interface. Each processor module also contains one optional portfor System Executive development or LAN support. The System Executivefor each processor module communicates with its companion Input/Outputsection for that processor via a shared memory interface. EachInput/Output section communicates with at least one Input/Output modulevia a triplicated communications bus. Each processor module alsocommunicates with at least one communications module via a triplicatedcommunications bus. The communication module provides TCP/IP networkingconnections to the development PC and DCS hosts. The communicationmodule also provides development and slave interface ports.

Several interconnect legs couple each of the processor modules togetherto form the System Controller. Each leg of the System controller iscontrolled by separate processor modules and each processor moduleoperates in parallel with the other two processor modules, as a memberof a triad. The input/output executive scans each input/output modulevia the input/output bus. As each input/output module is scanned, thenew input data is transmitted by the input/output module to processormodule via shared memory located on the printed circuit board supportingthe processor module and the input/output module.

The processor module stores the input data into an input table in itsmemory for evaluation by the application program.

Prior to the application program evaluation, the input table in eachprocessor module is compared with the input tables on the otherprocessor modules via the Channel 11. The Channel 11 is a three channelparallel to serial/serial to parallel communications interface with DMAcontroller, hardware loop-back fault detection, CRC checking andprocessor module to processor module electrical isolation.

The complete input data in the table for each MP/IOP module 1 istransferred to the other MP/IOP module 1 in the system and then “voted”by the System Executive firmware SX 15′. After the Channel 11 transferand input data voting has corrected the input values, the values areevaluated by the application program. The application program isexecuted in parallel on each processor module by the MPC860microprocessor which forms the processor module. The application programgenerates a set of output values based upon the input values, accordingto the rules built in to the program by the Control Engineer. Theprocessor section transmits the output values to the Input/Outputsection via a shared memory. The processor section also votes the outputvalues via Channel 11 access to detect faults, i.e. non-compliantcomponent. The input/output module separates the output datacorresponding to individual Input/Output modules in the system. Outputdata for each input/output module is transmitted via an Input/Output busto the Input/Output modules for application to field units.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 Control system overall block diagram

FIG. 2 Detailed overall block diagram

FIG. 3 I/O Module block diagram

FIG. 4 Main processor module block diagram

FIGS. 5A-5B Rail mount

FIG. 6 Interface block diagram

FIG. 7 MP/IOP board block diagram

FIGS. 8A-8B Flow of program support for application program

FIGS. 9A-9B FPGA block diagram

FIG. 10A Minimum system block diagram

FIG. 10B Large system block diagram

FIGS. 11A-11B Communication paths for data capture and timesynchronization

FIG. 12 Communication modules block diagram

FIG. 13 Enclosure diagram including heat dissipation pads and jackscrew

FIG. 14 Main processor board block diagram with dual power source

FIG. 15 Power board block diagram

FIG. 16 Dual board mounting structure and arrangement

FIG. 17 Profile of enclosure and interlock mechanism

FIG. 18 Faceplate covers

FIGS. 19A-19B Main processor

FIGS. 20A-20B Baseplate digital In base plate and connectors

FIGS. 21A-21B Baseplate digital out base plate and connectors

FIGS. 22A-22B Baseplate analog in base plate and connectors

FIGS. 23A-23B Baseplate registers out base plate and connectors

FIG. 24 FPGA register structure

FIG. 25 Time synchronization diagram

DESCRIPTION OF THE SPECIFIC EMBODIMENT

FIG. 1 is an overall block diagram of the control system which includesa Main processor 1, I/O modules 2, communication modules 3 and dualredundant power supplies 4.

Overview

FIG. 2, shows a typical system configuration in more detail, whichincludes triple MP/IOP modules 1 (Sometimes referred to interchangeablyas LMP/LIOP in the specification and drawings) having an MP(A) 1 a, anMP(B) 1 b and an MP(C) 1 c assembly and may include up to six I/Oassemblies of various types of I/O modules. Two I/O modules 2 a and 2 bare illustrated. Assemblies are configured into a system on a mountingbase plate as shown in FIGS. 5A and 5B using interconnect assemblies,extenders, I/O bus cables (used to join I/O columns), and I/O busterminators, I/O modules communicate with the MPs by means of atriplicated, RS485 bi-directions communication bus, called the I/O bus13.

As noted above the present invention comprises a fault tolerantcontroller 31 comprising a triple modular redundant (TMR) architecture.The controller includes three identical channels, Channel A, 13 a,Channel B, 13 b, and Channel C 13 c except for the power modules whichare dual-redundant. Each MP, MP(A), 1 a, MP(B), 1 b, MP(C), 1 c on thechannel independently executes the application program in parallel withthe other two MPs. Voting mechanisms qualify and verify all digitalinputs and outputs from the field 34; analog inputs are subject to amid-value selection process.

Each channel 13 is isolated from the others, no single-point failure inany channel 13 can pass to another. If a hardware failure occurs in onechannel 13, the faultily channel 13 is overridden by the other channels.Repair consists of removing and replacing the failed module in thefaulty channel while the controller is online and without processinterruption.

As shown in FIG. 2, each I/O module houses the circuitry for the threeindependent channels 13 a, 13 b, and 13 c each channel serviced by anFPGA 30 a, 30 b, 30 c, as shown in FIG. 3. Each FPGA 30 on the channelson the input modules reads the process data from the field circuitry 32a, 32 b, and 32 c and passes that information to the respective MPmodule 1.

The three MP/IOP modules 1 communicate with each other using ahigh-speed bus inter-MP bus called a channel 11. The system is a scanbased system and once per scan, the MP modules 1 synchronize andcommunicate with the neighboring MP modules 1 over the Channel 11. TheChannel 11 forwards copies of all analog and discrete input data to eachMP module 1. Each MP module 1 compares its input table data with theinput table data for all other MP modules 1. The MP modules 1 vote theinput data, execute the application program and send outputs generatedby the application program to the output modules 2 a, 2 b and 2 b′. Inaddition, the controller 31 votes the output data at the FPGAs 30 a, 30b and 30 c on the output modules as close to the field as possible todetect and compensate for any errors that could occur between theChannel 11 voting and the final output driven to the field 34. For eachI/O module 2, the controller 31 can support an optional hot-spare module2′ as shown in FIG. 2. If present, the hot-spare takes control if afault is detected on the primary module during operation. The hot-spareposition is also used for the online-hot repair of a faulty I/O modules.

The MP modules 1 each control a separate channel and operate in parallelwith the other two MPs. A dedicated I/O control processor IOX 17′ oneach MP/IOP module 1 as shown in FIG. 4 manages the data exchangedbetween the MP/IOP module 1 and the I/O modules 2. A triplicated I/O bus13, located on the base plates may be extended from one column of I/Omodules 2 to another column of I/O modules 2 using IO bus cables. Inthis way the system can be expanded. Each MP module 1 poles theappropriate channel 13 of the I/O bus 13 and the I/O bus transmits newinput data to the MP module 1 on polling the channel. The input data isassembled into an input table in the MP module 1 and is stored in memoryfor use in the voting process.

Referring to FIG. 2, each input table in each MP module 1 is transferredto its neighboring MP module 1 over the Channel 11. After this transfer,voting takes place. The Channel 11 uses a programmable device with adirect memory access to synchronize, transmit, and compare data amongthe three MP modules 1 a, 1 b and 1 c.

If a disagreement occurs, the signal value found in two of three tablesprevails, and the third table is corrected accordingly. Each MP module 1maintains data about necessary corrections in local memory. Anydisparity is flagged and used at the end of the scan by built-in faultanalyzer routines to determine whether a fault exists on a particularmodule.

Each of the MP modules 1 sends corrected data to the application programand then executes the application program in parallel with theneighboring MP modules 1. The application generates a table of outputvalues that result from the table of input values according touser-defined rules. The I/O control processor IOP 17 on each MP module 1manages the transmission of output data to the output modules 2 a bymeans of the I/O bus 13. Using the table of output values, the I/Ocontrol processor 17 generates smaller tables, each corresponding to anindividual output module 2 a where there are multiple output modules 2 aEach small table is transmitted to the appropriate channel of thecorresponding output module 2 a over the I/O bus 13. For example, MPmodule (A) 1 a transmits the appropriate table to channel A of eachoutput module 2 b and 2 b′ I/O bus(A) 13 a. The transmittal of outputdata has priority over the routine scanning of all I/O modules 2.

Each MP module 1 provides a 16-megabyte DRAM for the user-writtenapplication program, sequence-of-events (SOE) tracking, and I/O data anddata tables, diagnostics and communication buffers. The applicationprogram is stored in flash EPROM and loaded into DRAM for execution. TheMP modules 1 receive power from redundant 24 VDC power sources. In theevent of an external power failure, all critical retentive data isstored in NVRAM. A failure of one power source does not affectcontroller performance. If the controller loses power, theapplication-program and all critical data are retained.

In addition each MP module 1 can provide direct development andmonitoring computer 6 support (Development System) and Modbus 5communications. Each MP module 1 provides one (IEEE 802.3 Ethernet)Development System computer port for downloading the application programto the controller and uploading diagnostic information. One ModbusRE-232/RS485 serial port which acts as a slave while an external hostcomputer is the master. Typically, a distributed control system (DCS)monitors and optionally updates the controller 31 data directly throughan MP module 1 connection.

The triplicated I/O bus 13 is carried baseplate-to-baseplate usinginterconnect assemblies, extender modules, and I/O bus cables and thelike mounted on a rail 66 as shown in FIGS. 5A & 5B. The redundant logicpower distribution system is carried using interconnect assemblies andextender modules on the rail thus permitting expansion on the rail or tomultiple rails.

The Channel 11, which is local to the MP module baseplate, consists ofthree independent, serial links operating at 25 Mbaud. The TriBuschannel is used to synchronize the MP modules 1 at the beginning of ascan. Then each MP module 1 sends its data to its upstream anddownstream neighboring MP modules 1. The Channel 11 transfers input,diagnostic and communication data, compares data and disagreements areflagged by the MP modules 1 for the previous scan's output data andapplication program memory. A single transmitter is used to send data toboth the upstream and downstream MP modules 1 by a transmitting MPmodule 1. This facilitates reception of the same data by the upstreamprocessor and the downstream processor.

Field 34 signal distribution is local to each I/O baseplate. Each I/Omodule transfers signals to (in the case of an output module 2) or fromthe field (in the case of an input module 2) through its associatedbaseplate assembly. There are two I/O module slots on the baseplate tietogether as one logical slot as shown in FIGS. 5A and 5B; a firstposition holds the active I/O module 2 a and 2 b and the second positionholds the hot-spare I/O module 2 a′ and 2 b′. Each field 34 connectionon the baseplate extends to both active and hot-spare I/O modules 2 a′and 2 b′. Therefore, both the active module 2 a and the hot-spare module2 a′ receive the same information from the field 34 termination wiringin the case of Input and in the case of output module 2 b and the hotspare module 2 b′ are sent the same information in the case of output.

The triplicated I/O bus 13 transfers data between the I/O modules 2 andthe MP modules 1. The I/O 13 bus is carried on a DIN mounting rail 66,as shown in FIGS. 5A and 5B and can be extended to multiple DIN rails66. Each channel 13 of the I/O bus 2 runs between one MP module 1 andthe corresponding channel on the I/O module 2.

Logic power for the modules on each DIN mounting rail 66 draws powerfrom the rails through redundant DC-DC power converters. Each channel ispowered independently from these redundant power sources.

The MP/IOP module 1 monitors each of the three input channels 13 a, 13 band 13 c measures the input signals from each point on the baseplateasynchronously, determines the respective states of the input signals,and places the values into input tables A, B and C respectively. Eachinput table in each MP module 1 is interrogated at regular intervalsover the I/O bus 13 by the IOP processor 17 located on the correspondingMP/IOP module 1, for example, MP module A (1 a) would interrogate InputTable A 1 over I/O Bus A (13 a).

The I/O modules are specific in application or function andfunctionality may be expanded as required by the addition of additionalfunctional modules. Referring to FIG. 6, the interfaces for thecontroller 31 are shown to include I/O modules 2 configured as a DigitalInput Module 2 a (DI), a Digital Output module, 2 b (DO) an Analog Inputmodule 2 c (AI) an Analog Output module 2 d (AO), a Relay Output module2 e (RO) and a Relay Input Module 2 f (RI).

The Digital (Discrete) Input Module 2 a contains the circuitry for threeidentical channels 13 as shown in FIG. 3 as 13 a, 13 b and 13 c (A, B,and C). Although the channels reside on the same module 2, they arecompletely isolated from each other and operate independently. Eachchannel 13 contains an application-specific integrated circuit (ASIC)which handles communication with its corresponding MP module 1, andsupports run-time diagnostics. Each of the three input channels measuresthe input signals from each point on the baseplate asynchronously,determines the respective states of the input signals, and places thevalues into input tables A, B and C respectively. Each input table isinterrogated at regular intervals over the I/O bus by the I/Ocommunication processor located on the corresponding MP, for example, MPA interrogates Input Table A over I/O Bus A as shown in FIG. 2. Aredundant or hot spare is illustrated as 26′.

Special self-test circuitry is provided to detect and alarm all stuck-atand accuracy fault conditions in less than 500 milliseconds and allowsunrestricted operation under a variety of multiple fault scenarios.

The input diagnostics are specifically designed to monitor devices whichhold points in one state for long periods of time. The diagnosticsensure complete fault coverage of each input circuit even if the actualstate of the input points never changes.

The DO (Digital Output module) module 2 b also contains the circuitryfor three identical, isolated channels 13, Each channel and includes anASIC which receives its output table from the I/O communicationprocessor 17 on its corresponding main processor MP module 1. All DOmodules 2 b use special quad output circuitry to vote on the individualoutput signals just before they are applied to the load. This votercircuitry is based on parallel-series paths which pass power if thedrivers for channels A and B or channels B and C, or channels A and Ccommand them to close. In other words, 2 out of 3 drivers are voted“on”. The quad output circuitry provides multiple redundancy for allcritical signal paths, guaranteeing safety and maximum availability.

A DO module executes an output voter diagnostic (OVD) routine at apredetermined time on each point. OVD detects and alarms two differenttypes of faults. The first is “points”—all stuck-on and stuck-off pointsare detected in less than 500 milliseconds. The second is “switches”—allstuck on or stuck-off switches or their associated drive circuitry aredetected. During OVD execution, the commanded state of each point ismomentarily reversed on one of the output drivers, one after another.Loop-back on the module allows each ASIC to read the output value forthe point to determine whether a latent fault exists within the outputcircuit. The output signal transition is less than 2 millisecond and istransparent to most field devices. OVD is designed to check outputswhich typically remain in one state for long periods of time. The OVDstrategy for a DO Module ensures full fault coverage of the outputcircuitry even if the commanded state of the points never changes.

On an AI Module 2 c, as shown in FIG. 6, each I/O FPGA 30 on channel 13measures the input signals asynchronously and places the results into aninput table of values. Each input table is passed to the associated MPmodule 1 using the corresponding I/O bus 13. The input table in each MPmodule 1 is also transferred to its neighbors across the Channel 11. Amiddle value is selected by each MP module 1, and the input table ineach other MP module 1 is corrected accordingly. In TMR mode, themid-value data is used by the application program; in duplex mode, anaverage is used. An analog output (AO) module may also be included foranalog adjustment of an analog driven parameter.

The Relay Output (RO) and Relay Input (RI) Module is a non-triplicatedmodule for use on non-critical points which are not compatible withhigh-side, solid-state output switches; for example, interfacing withenunciator panels. The RO Module receives output signals from the MPs oneach of three channels. The three sets of signals are then voted, andthe voted data is used to drive the 32 individual relays. Each outputhas a loop-back circuit which verifies the operation of each relayswitch independently of the presence of a load. Ongoing diagnostics testthe operational status of the RO Module.

Special self-test circuitry is provided to detect and alarm all stuck-atand accuracy fault conditions in less than 500 milliseconds.

DETAILED DESCRIPTION

Each I/O module 2 is designed to operate directly from redundant 24 VDSpower sources as shown in FIG. 14. Logic power is carriedbaseplate-to-baseplate, allowing a signal logic power connection percolumn. The power conditions circuitry is protected againstover-voltage, over-temperature, and over-load conditions. Integraldiagnostic circuitry checks for out-of-range voltages andover-temperature conditions. A short on a channel 13 disables the powerregulator rather than affecting the power sources.

The controller 31 of the present invention incorporates integral onlinediagnostics. These diagnostics and specialized fault monitoringcircuitry are able to detect and alarm all single fault and mostmultiple fault conditions. The circuitry includes but is not necessarilylimited to I/O loop-back, watch-dog timers, and loss-of power sensors.Using the alarm information, the user is able to tailor the response ofthe system to the specific fault sequence and operating priorities ofthe application.

Each module can activate the system integrity alarm, which consists ofnormally closed (NC) relay contacts on each MP/IOP module 1. Any failurecondition, including loss or brown-out of system power, activates thealarm to summon plant maintenance personnel.

The front panel of each module provides light-emitting-diodes (LED) 41indicators as shown on FIG. 16 that show the status of the module or theexternal systems to which it may be connected, PASS, FAULT, and ACTIVEare common indicators. Other indicators are module—specific.

Normal maintenance consists of replacing plug-in modules. A lightedFAULT indicator shows that the module has detected a fault and must bereplaced.

All internal diagnostic and alarm status data is available for remotelogging and report generation. Reporting is done through a local orremote host computer.

Additional special features include fault testing of channels through aloop-back through the base plate to ensure that the transmitting moduleis accurately transmitting data, and status information.

The MP/IOP modules 1 running in parallel rendezvous each scan to vote,and run the application program. At each rendezvous the MP/IOP modules 1are time synchronized by the adjustment of their time clocks by anamount required to bring them into synchronization. Dependent on thedisparity between time clocks either a positive or a negative adjustmentis made to those clocks out of synchronization.

Referring again to FIG. 4, the preferred main processor (MP, 15) CPU isa Motorola MPC860 operating at 50 MHz with PLL enabled. The oscillatortolerance is 25 ppm. The MP 15 uses the following components of theMPC860, RISC CPU, 4 Kbyte data cache, 4 Kbyte instruction cache, MMU,Memory controller, Time base used for a real time clock, Interruptcontroller used for all serial and DMA channels, Channel 11, andsynchronization system interrupts, the PC 860, Parallel port is used forLEDs and miscellaneous I/O, Communications Processor and othercommunicators.

The Main Processor, MP/IOP module 1 comprises at least twosemi-independent sections, the MP 15 (main processor) and the IOP 17(Input/Output Processor). Also provided are a Modbus port 5 which is aModicon protocol port. The system supports acting as a slave to the port5 communication link. A development system port 6 is also providedthrough which the application program developed may be downloaded from adevelopment PC or other computer and the controller 31 monitored.Communications between the main processor MP 15 sections and other mainprocessor sections of other MP/IOP modules 1 takes place over theChannel 11. Communication between the Input/Output, IOP sections 17,with other processor IOP sections 17 takes place over the IOP bus 14.Communications between the MP/IOP module 1 and communications CM module3 take place over the LCB bus 9.

Each MP/IOP module 1 is capable of operating in SINGLE, DUAL and TMR(Triple Modular Redundant) modes. Each MP/IOP module 1 may control up to56 I/O base-plate assemblies (LIO modules 2). The number of I/Obase-plate assemblies varies based upon system options and requirementsfor a given industrial or other installation.

The IOP 17 uses the following components of the MPC860: a RISC CPU, 4Kbyte data cache, 4 Kbyte instruction cache, Memory Management Unit,Memory controller, a Time base, use for IOX 17′ real time clock,Interrupt controller used for all serial and DMA channels. Parallel portused for IOP 17 leg synchronization, and LEDs and miscellaneous I/O, aCommunications Processor, BDM Port, SCCI used for remote/expansion IOPbus, SCC2 used for the LIO bus, SCC3 used for upstream IOPcommunications, SCC4 used for downstream 10P 17 communications, SCM2used for very low level hardware and IOX 17′ debug & development. TheIOP 17 clock is derived from the MP 15 50 MHz clock.

As shown in FIG. 4 the MP 15 is dedicated to SX 15′ (the systemexecutive) and associated firmware, the IOP 17 is dedicated to IOX 17′(the input output executive) and associated firmware. Each MP 15 sectionalso includes one optional 802.3 port 10 for SX 15′ development or LANsupport. Each MP 15 communicates with its associated IOP 17 via a sharedmemory interface 18 to memory unit 16.

The primary function of SX 15′ is to provide an execution environmentfor a application program developed by a Control Engineer for aparticular industrial control system. To provide this environment, theSX 15′ is engaged in performing the following steps as shown in FIGS. 8Aand 8B:

1. Receiving Inputs from the IOP 17, step 301;

2. Voting Inputs for the application program, step 302;

3. Downloading application programs (All and Changes), step 303;

4. Executing application programs, step 304;

5. Sending outputs to the IOP 17, step 305;

6. Sending Configuration Information to the IOP 17, step 306;

7. Processing messages from Communications Modules LCM, step 307;

8. Verifying the integrity of the hardware, step 308;

9. Reading Modbus Slave Requests, step 309; and

10. Return for more inputs, step 310.

The SX 15′ firmware executes the application program generated by theuser and down loaded from a development PC 35 or other computer systemas shown in FIG. 10A. The application program uses Digital and AnalogIOP Inputs and sends outputs to the input/output and communicationboards. SX 15′ controls timing and synchronization between the three MPs15, voting of input data and system data, detection and analysis of I/Ofaults and internal faults, and communication with the developmentsystem 35 and a diagnostic port.

The SX 15′ runs in parallel on each of the three Main Processors 1 a, 1b and 1 c controls timing and synchronization between the three MPmodules 15 and the voting of input data and system data. TheseProcessors are kept in real time synchronization by a combination of thetime specific hardware and software functions. SX 15′ uses real timesynchronization to rendezvous all of the Main Processors at a maximumscan rate. The scan rate is selectable by the user within the range of10 ms to 450 ms. Once the rendezvous occurs, each SX 15′ transfersinformation tables between the three Main Processors. SX 15′ thendetermines what functions need to be done during the scan. These includeupdating memory, running an application program, and the like.

Referring again to FIG. 2 and FIG. 4, the IOX 17′ firmware executes on aseparate 50 MHz MPC860 CPU, located on the MP/IOP module 1. There arethree identical copies of IOX 17 firmware, on each MP/IOP module 1.These copies are referred to as legs A, B and C based on the MP 15 theyare running on. Each leg or channel (between MPs) has an upstream legand a downstream leg, referred to as US and DS. The following tabledefines the Upstream, US, and Downstream, DS, mapping functions. Therelationship is illustrated in FIG. 11 showing upstream and downstreampaths. Where u=upstream, d=downstream, m=me, T=TTS pulse, L=Loop-backcapture, C=Capture.

As shown in FIG. 10A, the typical minimum system of the presentinvention includes three MP/IOP modules; 1 a, 1 b and 1 c. At least oneof these modules, 1 a, may be connected to a application programdevelopment computer 35 over a development connection 6 to the systemexecutive, SX 15′. This connection permits a download of the applicationprogram developed on the development system 35 to at least one of thethree processors 1 a, 1 b, 1 c which loads the program to the other two.Additionally, an interface over the Modbus 5 for each of the processorspermits distributed processor control system (DCS) and human machineinterface (HMI) communications over RS232/RS485 bus ports, 5 b and 5 c.Each of the processors communicates over an LIO bus 13 on independentinterconnection lines 13 a, 13 b and 13 c as shown in FIGS. 10A and 10B.Each of the LIO bus connections interfaces with the LIO modules 2 a and2 b, shown by way of example, each of which have triplicated FPGAs 30 a,30 b, and 30 c over bus 13 a, 13 b and 13 c. Each FPGA is coupled to thefield circuitry 32 a, 32 b and 32 c respectively which receives fieldinputs 34 for the particular control system being monitored. The I/Omodules may as noted above be configured for particular services, suchas DI, DO, AI, AO, RO, RI and the like.

With reference to FIG. 10B, an alternate configuration of thetriplicated main processors 1 a, 1 b and 1 c is shown utilizing dualcommunication modules 3 a and 3 b which provide the Modbus andDevelopment serial links, but in addition provide external communicationlinks for external communications. In this configuration the Modbus 5and Development 6 ports on the MP/IOP modules 1 a, 1 b, and 1 c aredisabled. Each of the LCM modules 3 a and 3 b communicates with each ofthe respective MP/IOP modules 1 over communication lines 9 a, 9 b and 9c which are coupled to the communication bus (LCB) of each of the mainprocessors. FIG. 10B also shows additional LIO modules 2 c and 2 dattached to the LIO bus to illustrate that multiple LIO modules 2 may beconnected on the same LIO bus 13.

While the system of the present invention is shown as triplicated MP/IOPmodules 1, multiple LIO modules 2 and optionally one or more LCM modules3, other configurations are possible to provide more or less,redundancy. As shown in FIG. 12, the LCM module 3 provides two 802.3TCP/IP networking connections 24 (for peer to peer linking) and 25 (fordevelopment system 35 or DCS hosts linking). The LCM also providesPS232/RS485 ports 26, 27, and 28 for supplemental bus and developmentsystem linking. The LCM is based on a Motorola MPC860T and MC68360 whichis used as a communications co-processor.

The system may also run with only one each of the various modules orcombinations of multiple MP/IOP modules 1, LCM modules 3 or LIO modules2. The System Executive, SX 15′ of each MP/IOP modules 1 is responsiblefor executing the application program downloaded from the Development PC35. The System Input/Output Executive, IOX 17′, communicates with theFPGAs 30 of the LIO modules 2 and the SX 15′. Both SX 15′ and IOX 17′are resident on the MP/IOP module in the MP 15 section and the IOP 17section respectively. The LIO modules convert physical inputs andoutputs to communication messages.

The MP 15 memory 16 includes an FPGA 77 as shown in block diagram formin FIGS. 9A and 9B which contains the following MP/IOP functions:Channel 11 management, synchronization system management, the MPwatchdog, the MP Hard reset management, the IOP watchdog, the IOP Hardreset management, Expansion flash prom decode routine, Modbus/LCMchannel MUX, Fault LED control, and Mode LED control. As shown in FIGS.9A and 9B, the major block descriptions of the FPGA 77 software is asfollows:

Rx_channel, 80 VHDL module containing: Rx_recvr, Rx_pith, Rx_crc andRx_ctrl. This module is used twice, once for the upstream channel andonce for the downstream channel.

Rx_recvr, 80 a Dual 5 bit de-serializer, dual 5b4b decoder, symboldecoder and byte strobe generation. Operates from the received clock.

Rx_pllh, 80 b Byte synchronization digital phase lock loop. Synthesesbyte strobes from the received byte strobe. Operates from the NPC860 50Mhz clock divided by 4.

Rx_crc, 80 c Calculates and checks the received CRCs, based upon anibble polynomial lookup table for CRC32. Operates from the MPC860 50Mhz clock divided by 4.

Rx_ctrl, 80 d Receive state machine. Decodes and sequences receivedbytes and request writes to the RX FIFO. Detects and handles receivechannel errors. Operates from the MPC860 50 Mhz clock divided by 4.

Tx_channel, 81 VHDL module containing: Tx_xmitr, Tx_crc and Tx_ctrl

Tx_xmitr, 81 a Dual 4b5b encoder, symbol encoder, dual 5 bit transmitshift register and byte strobe generator. Detects and handles Transmitchannel errors. Operates from the MPC860 50 Mhz clock divided by 4.

Tx_crc, 81 b Calculates and sends the transmit CRCs. Based upon a nibblepolynomial lookup table for standard CRC32. Operates from the MPC860 50Mhz clock divided by 4.

Tx_ctrl, 81 c Receive state machine. Generates packet symbol sequences,header, header to data pad and data field sequence. Requests and readsbytes from the TX FIFO. Operates from the MPC860 50 Mhz clock divided by4.

Rx_fifo, 82 Contains 4-32 by 8 dual port SRAMs organized as two 16 by 32FIFOs. Also contains the receive channel byte to 32 bit word steeringMUX.

Tx_fifo, 83 Transmit channel FIFO, contains 4-32 by 8 dual port SRAMsorganized as one 16 by 32 FIFO and 1 by 32 bit word used for diagnosticCRC word storage. 15 by 32 locations spare.

Tb_dma, 84 DMA bus controller and channel arbiter. Handles requests fromthe Transmit and receive channels for FIFO bus read and writes. Controlsthe MPC860 side on the Rx_fifo, Tx_fifo and all DMA address pointers(Tb_addr). Communicates via signal pins with the external Bus PAL forDMA transfers. Operates from the MPC860 50 Mhz clock divided by 2.

Tb_addr, 85 All DMA pointers: Transmit buffer descriptor page registerTXBDP, Transmit buffer descriptor index pointer TXBDI, Upstream bufferdescriptor page register UPBDP, Upstream buffer descriptor index pointerUPBDL Downstream buffer descriptor page register DNBDP, Downstreambuffer descriptor index pointer DNBDI, MPC860 Address bus MUX andperipheral bus read back MUX.

Tb_regs, 86 Holds the Miscellaneous control register, Transmit channelcontrol register, Upstream and downstream control, Channel 11 interruptsand the peripheral bus interface.

Tt, 87 synchronization system. Contains entire synchronization systemfunctionality described hereafter plus 2 32 by 8 dual port SRAMs usedfor capture registers. Interfaces to and peripheral bus through Th_regs.Operates from the MPC860 50 Mhz clock divided by 2.

tb_misc, 88 Contains LED controls, expansion flash prom decode, MP 15reset, IOP 17 reset, MP 11 watchdog timer and IOP 17 watchdog timer.Operates from the 16 mhz-baud clock.

tb_a4, 89 FPGA 77, also contains clock buffers, parity generator and I/Obuffers

FIGS. 11A and 11B shows the interconnection of the main processormodules MP/IOP module 1. FIGS. 11A and 11B illustrates an upstream MP 90(U) transmitting a pulse 90 f (T) over path 90 a (ud) to the downstreamprocessor 92 (D) where it is captured by downstream processor 92 at itsdownstream capture register 92 j (dC); over path 90 b to its upstreamloop back capture register 90 e (uL); along path 90 j (mu) where it iscaptured by the My processor 91 (M) capture register 91 h (uC) and overpath 90 d to its downstream loop back capture register 90 g (dL).

Similarly, the My processor 91 (M) is shown transmitting a pulse 91 f(T) over path 91 (um) a to the upstream processor 90 (U) where it iscaptured by downstream processor 90 at its downstream capture register90 j (dC); over path 91 b to its upstream loop back capture register 91e (uL); along path 91 c (md) to the downstream processor 92 (D) tocapture register 92 h (uC) and over path 91 d to its downstream loopback capture register 91 g (dL).

The downstream MP 92 (D) is shown transmitting a pulse 92 f (T) overpath 92 a (dm) to the next downstream processor 91 (M) where it iscaptured by downstream processor 91 at its downstream capture register91 j (dC); over path 92 b to its upstream loop back capture register 92c (uL); along path 92 c (du) to the upstream processor 90 (U) to captureregister 90 h (uC) and over path 92 d to its downstream loop backcapture register 92 g (dL). TABLE I Upstream and Downstream relation LegUS (leg) DS (leg) A C B B A C C B A

The IOP 17 which contains the IOX 17′ provides the following serialcommunications interfaces: an LIO Bus, a Diagnostic Channel, an RS232Debug port, a BDM port, a 802.3 10 BaseT Ethernet expansion IOP 17 bus,RS485 expansion IOP 17 bus, an I²C channel for communications with theTemperature sensor.

Each IOX 17′ implements the complete logic for one of the three legs (A,B or C). It communicates with the other IOX 17′ legs through twomechanisms: a synchronization signal and data messages through a serial,HDLC diagnostic bus.

The IOX 17′ internal execution architecture is based on deterministic,fixed duration “I/O scans”. The IOX 17′ design allows for any predefinedscan duration, but is set to use a 1 millisecond scan time. During eachI/O scan, execution proceeds in two modes: foreground and background.

The foreground mode is implemented as an interrupt service routine,which takes up most of the I/O scan durations. An internal MPC860 timerinterrupt is used to switch the CPU to foreground mode. This I/O scaninterrupt is synchronized by software with upstream and downstream IOXsections 17′, ensuring that foreground execution on all three legsstarts within a maximum of 2 μsec of each other.

Following these tasks, the CPU reverts to the background mode, whichimplements the synchronizing IOX 17′ system time with the SX 15′ systemtime informing SX 15′ that IOX 17′ is still operational processingcontrol messages that SX 15′ may have placed in the shared memory, andprocessing input from, and output to, the debug port.

A diagnostic channel provides a communications link between the IOPlegs. The MP 15 and IOP's section 17 leg addresses are read throughMPC860 parallel port pins. TABLE II Leg Address encoding: MPC860 PortPin Leg number PB14 PB15 PB16 Leg A 0 1 1 Leg B 1 0 1 Leg C 1 1 0 Badaddress All other values

The MP 15 and IOP 17 node addresses are read through MPC860 parallelport pins. Both the MP 15 and IOP 17 are connected to the samebase-plate address plugs.

Each redundant leg or channel 13 of the system is mechanically andelectrically isolated from adjacent legs in an acceptable mechanicalisolation, which is defined as at least equivalent to the trace-to-tracespacing required to achieve 800 VDC electrical isolation. Otherisolation techniques such as opt-isolation at all leg-to-leg interfacesmay be used as an alternative provided the preferred VDC is achieved.

In the event of an MP/IOP module 1 failure, the triad, via softwarecontrol, is dissolved dynamically and the remaining two re-configuredinto a dual-master configuration. A hot replacement MP/IOP module 1 isdynamically “re-educated” by transferring re-education data includingapplication program and data over the Channel 11 on insertion.

Enclosure and Mounting

Referring to FIG. 13, the MP/IOP modules 1, LIO 2 modules, LCM 3 modulesare each housed in a separate configurable enclosure or housing 29,which receives the circuit boards which comprise the different modules.The same form of housing 29 may be used for each module by simplychanging the face plate information for the particular module. The cover20 and the base 21 of the housing 29 are shown in FIG. 13. Both thecover 20 and the base 21 are provided with a thermal conductive pad ormedium 36 which is electrically non conductive. A suitable medium 36used for this purpose is a GAP PAD™ 1500 which is a conformablethermally conductive material for filling air gaps. The GAP PAD™ 1500medium 36 used in this invention is obtainable from the BergquistCompany at 5300 Eldina Industrial Boulevard, Minneapolis, N. Mex. 55439and the Bergquist Company has been granted patents on such materials asis shown in U.S. Pat. No. 5,679,457 which is incorporated herein byreference.

The thermally conductive medium 36 is applied to the inner surfaces ofthe housing 29, which preferably includes at least the two majorsurfaces. As illustrated, four surfaces are covered. Where increasedthermal conductivity is desired all or any portion of the internalsurfaces may be covered by medium 36. Each functionally-specific moduleuses the same general circuit board for providing redundant power. Thecharacter or the functionality of the particular module is determined bythe module board for the various modules, as previously described, thatis the electronic circuit board which implements the MPt/IOP module 1,LCM module 3 or the various types of LIO modules 2. FIG. 14 and FIG. 15show the block diagram for the power board 4 and the MP/IOP module 1 forexample.

Referring again to FIG. 13, the molded cover 20 of the housing 29includes a planar cover mounting surface 38 for receiving the thermalconductive medium 36, and a face plate 39 mounted generally at rightangles to the mounting surface 38. The face plate 39 is provided with aseries of LED conduits 40 that may be filled with fiber optic tubes orplastic inserts, or other light transmissive medium or a cover forpermitting light from LED's 41 which are mounted on the module circuitboards 54 to pass from the circuit board to the surface of the faceplate39 for viewing. While holes may be left open in the cover 20 face plate39, dust and debris from the industrial environment may contaminate thecircuitry. Accordingly, these conduits are preferably filled to seal thehousing 29. The extruded cover 20 of the housing 29 has a plurality ofthermal dissipating fins 61 on an outer surface 38 a. The face plate 39also has a hole 74 a for receiving a jack screw 50.

The base 21 of the housing 29 includes a planar base mounting surface 43and a base 44 which has a plurality of connector holes 45 and groundingpin holes 46 for electrical connectors to a base plate 49. The groundingpins 47 a and 47 b are elongated as shown in FIG. 16 so that when thehousing 29 is mounted to the base plate 49, the grounding pins 47 engageprior to engagement of the electrical connectors 48. This permits thehousing 29 to be grounded before the power is applied to the modulethrough engagement with the connectors 48. The base 21 further includesopposing sides 59 a and 59 b which enclose the housing 29 when the sameis assembled with the cover 20. The base is also provided with thermaldissipating base fins 60 mounted on the outer surface 43 a of the basemounting surface 43. In addition, grounding pin placement only permitsone-way insertion.

To allow the MP/IOP module 1 hardware to fit into the system packaging,the MP/IOP module 1 design is separated into two printed circuit boardassemblies as shown in FIG. 16. These are the functionality board 51 forthe particular module being implemented and the power interface board 56which are mounted in the system package in the form of a sandwich. A 50pin connector connects the two PCBs at one end.

As shown in FIG. 16, the power board 56 and the functionality board 57are each sized to fit into the housing 29 and are connected in the formof a circuit board sandwich 37 with all of the inter board connectors 94at one end. Also shown in the schematic of the circuit board sandwich 37the data signals 54 are input and output at one end and visual signals55 generated by LED's 41 or any other source of light are output at theat the other. The power board 56 and the functionality board 57 areelectrically connected at the end near the front of the housing 29 andall of the electrical connections are disposed at the rear of thehousing 29 and are externally accessible. The board sandwich 37 may bemounted inside the housing in any conventional manner provided that heatgenerated by the circuit boards is transmitted out of the housing. Thethermally conductive medium should therefore be in contact with thecircuit board and the inner surfaces of the housing. As shown in FIG.13, the base 21 includes mounting pads 71 for fastening the powercircuit board 56 inside the housing which are disposed in the center atthe four corners of the planar mounting surface. Only three of themounting pads 71 are visible. It should be noted that other thermalcontrol mechanisms such as coolant tubes and the like may also be usedfor heat dissipation within the housing 29.

As shown in FIG. 17, the cover 20 face plate 39 is also provided with aflexible Mylar cover 42 which is retained in opposing slots 58 a and 58b on the front of the base and are used to identify the type of module(i.e. its function). In this respect, the conduits 40 are made toaccommodate all of the positions for the LED's 41 for all configurationsof LED's for each type of module. The Mylar cover 42 covers thoseconduits 40 not used for the particular functionality intended.

The major elements of the control system include field replaceablemodules housed in the protective metal housing 50. These modules includea Main Processor Module (MP 15), I/O Modules including a Digital InputModule (DI), a Digital Output Module (DO) a Relay Output Module (DI), anAnalog Input Module (AI) an Analog Output Module and Extender Module(EM) and such other modules as may be necessary or appropriate.

Each of these modules is fully enclosed to ensure that no components orcircuits are exposed even when the module is removed from the baseplate.Offset baseplate connectors make it impossible to plug a module in tothe baseplate connectors in the incorrect position. In addition, keys oneach module prevent the insertion of modules into the incorrect slots.

FIGS. 18A, 18B, 18C, 18D and 18F shows typical MYLAR cover 42 for theface plate for the housing 29 for each of the various modules withindicia for functions identification and openings 95 aligned with theLEDs 41 of the specific functionality board and with opaque areascovering unused channels 40. The specific indicators used for the MP/IOPmodule 1 are shown in the following Table III, although other indicatorsmay be used as required. Many of these same indicators may be used inother modules. TABLE III MP/IOP indicators Front Panel Indicators StatusPower Control- Function LED Indicator Color up state led By Module PassGreen Off Not Fault Status Fault Red On MP | IOP Active Green Off MPMode Run Mode Green On MP Remote Mode Green On MP Program Mode Yellow OnMP Stop Mode Yellow On MP Alarms Field Power Red On MP System Power RedOn MP System Alarm Red On MP Program Alarm Blue On MP Over TemperatureRed Off MP Lock Red On/Off MP Communi- TX/RX Reserved Green/Green Off Hwcations Status TX/RX IO bus Green/Green Off Hw TX/RX COMM BusGreen/Green Off Hw TX/RX Modbus Green/Green Off Hw LINK/TX/RXGreen/Green/ Off Hw Development Green NetworkHw = Hardware circuit.Note 1 MP or IOP, not both, under firmware control.

The module status indicators display the operational status on theMP/IOP 1 module. IOP 17 status is passed to the MP 15 via the sharedmemory interface.

-   Pass—Indicates that both MP 15 and IOP 17 sections have passes all    diagnostics. PASS is the inverse of FAULT, and can be read on both    MPC860s PA8. PASS is active low. No user action required.-   Fault—Indicates a fault was detected on the MP 15 or IOP 17    sections. The user is expect to replace the module. The fault    indicator is forced ON by a MP/IOP module 1 “hard” reset, or MP 15    or IOP 17 watchdog timer time-out or the FAULT port bit PA11 on the    MP or IOP MPC860. The FAULT bit is active high. The FAULT bit is    pulled up via a 10 k resistor, so that it defaults to the faulted    state. Note: If the fault is detected in a non critical portion on    the MP, such as the Debug port or Flash prom, or the MP has    re-educated too many times due to transient faults, it is permitted    for the MP 15 to continue running is the Fault—Active state. See SX    fault handling.-   Active—Indicates the MP 15 is running the application program. The    MP 15 flashes Active LED once for each application program scan    executed. SX firmware shall control the ON duty cycle to ensure the    LED is visible, even for very fast application programs. The ACTIVE    LED is driven from MPC860 port bit PA10, active high.    Mode Indicators-   Run Mode—Indicates the System of the present invention is in “Run”    mode. Run is driven from the Channel 11/synchronization system FPGA    77, see MCR register. The led defaults to ON during hardware reset.-   Remote Mode—Indicates the System of the present invention is in    “Remote” mode. Remote is driven from the Channel 11/synchronization    system FPGA 77. The led defaults to ON during hardware reset.-   Program Mode—Indicates the System of the present invention is in    “Program” mode. Program is driven from the Channel    11/synchronization system FPGA 77. The led defaults to ON during    hardware reset.

Stop Mode—Indicates the System of the present invention is in “Stop”mode. Stop is driven from the Channel 11/synchronization system FPGA 77.The led defaults to ON during hardware reset.

System Status Indicators

-   Field Power—Indicates that a 24 v field power input on one or more    110 module is missing. If the field power alarm is on, the system    alarm is illuminated by SX 17′. Development or Trilog must be    queried by the user to determine the actual module(s) reporting the    alarm condition. FP_ALRM is active high on PB29.-   System Power—Indicates that there is a 24V logic power input missing    on one or more MP, I/O or CM module. Development or Trilog must be    queried by the user to determine the actual module(s) reporting the    alarm condition. If the logic power alarm is on, the system alarm is    illuminated by SX 17′. SP_ALRM is active high on PB28.-   System Alarm—Indicates that a fault or error condition is present in    the System of the present invention. Development or Trilog must be    queried by the user to determine the actual module(s) reporting the    alarm condition. System alarm is driven by the MP port bit PA9.    System alarm is active high and pulled up.-   Program Alarm—Is driven by the application program to indicate an    alarm condition detected by the application program, typically    bypassed points. Program alarm is driven by the MP 15 port bit PD5.    System alarm is active high and pulled up.-   Over Temp.—Indicates an MPC860 junction over temperature. Over temp    is driven directly from the temperature monitor IC. SX 17′ programs    the trip temperature via the I²C channel.-   Lock—Indicates the module is not locked into its base-plate. The    unlock status bit is readable on both MPC860's port bit PC9. Unlock    is active high and pulled up.    Module Communications Indicators

Communications indicators are provided to aide the user/installer introuble shooting cable installation problems.

-   Reserved TX/RX—Flashes when an expansion IOP 17 is communicating,    over the RS485 IOP bus.-   Bus TX/RX—Flashes when the IOP 17 is communicating on the LIO bus.-   COMM Bus TX/RX—Flashes when the MP 15 is communicating to either    LCM.-   Modbus TX/RX—Flashes when the MP 15 is communicating on it's local    RS232/RS485 Modbus port.-   Development Link—Indicates the MPs 15 10 BaseT twisted pair receiver    has established a hardware connection over RX+ and RX− signals with    the Ethernet hub. Note: The hub should also contain a Link LED to    indicate a hardware connection has been established with the MPs TX+    and TX− twisted pair signals.-   Development TX/RX—Flashes when the MP 15 is communicating on it's    802.3 10 BaseT Development network. Flashes when the MP 15 is    communicating on it's 802.3 TriLan port or when the LRXM or    expansion IOP is communication over it's 802.3 fiber optic port.

The table IV below lists the conditions represented by the topindicators on the DI front panel, FIG. 18B, and provides a descriptionand a recommended action for each condition. An X represents a neutralindicator. TABLE IV Top Indicator Conditions Pass Fault Active LockDescription Action On Off On Off Module is operating normally. No actionis required. On Off Off Off Possible conditions: Application program hasnot been If module is the hot spare, loaded into the MP. no action isrequired. Application program has been If module is active, replaceloaded into the MP, but has not module. been started up. Module has justbeen installed and is currently running start-up diagnostics. The othermodule is active. Off On X Off Possible conditions: Module may havefailed. See mode indicator status for power-up states. Module may be inthe process of If module's PASS indicator power-up self-test. does notgo on within five minutes, replace module. Module has detected a fault.Module is operational, but should be replaced X X X On Module isunlocked from the Lock module. baseplate. On On X X Indicators/signalcircuitry on the Replace module. module are malfunctioning

The following table V lists the conditions that can be represented bythe Field Power indicator. TABLE V Field Power Indicator ConditionsField Power Description Action On Field power from one To isolate themissing power or more of the source, use the Development redundantsources System computer Diagnostic Panel. is missing. Correct theproblem in the field circuit. If these steps do not solve the problem,replace module. Off Field power is No action is required. operatingnormally.

The following table VI lists the possible conditions that can berepresented by a point indicator. TABLE VI 32 Point Indicator ConditionsPoint (1-32) Description On Field circuit is energized. Off Fieldcircuit is not energized.

The table VII below lists the conditions represented by the topindicators on the DO front panel (see FIG. 18C) and provides adescription and a recommended action for each condition. An X representsa neutral indicator. TABLE VII DO Front Panel Pass Fault Active LockDescription Action ON Off On Off Module is operating normally. No actionis required. On Off Off Off Possible conditions: Application program hasnot been If module is the hot spare, loaded into the MP. no action isrequired. Application program has been If module is active, replaceloaded into the MP, but has not module. been started up. Module has justbeen installed and is currently running start-up diagnostics. The othermodule is active. Off On X Off Possible conditions: Module may havefailed. See mode indicator status for power-up states. Module may be inthe process of If module's PASS indicator power-up self-test. does notgo on within five minutes, replace module. Module has detected a fault.Module is operational, but should be replaced X X X On Module isunlocked from the Lock module. baseplate. On On X X Indicators/signalcircuitry on the Replace module. module are malfunctioning

The following table VIII lists the conditions that can be represented bythe Power/Load indicator. TABLE VIII Power/Load Indicator. ConditionsField Power Description Action On For at least one point, To isolate thesuspected the commanded state and point, use the Development themeasured state do System computer Diagnostic not agree. Panel. Todetermine the output point's commanded state, use the Development Systemcomputer Control Panel. To determine the output's actual state, use aVoltmeter, then correct the problem in the external circuit. If thesesteps do not solve the problem, replace module. Off All load connectionsare No action is required. functioning properly.

The following table IX lists the possible conditions that can berepresented by a point indicator. TABLE IX 16 Point Indicator ConditionsPoint (1-16) Description On Field circuit is energized. Off Fieldcircuit is not energized.

The table X below lists the conditions represented by the top indicatorson the AI front panel (see FIG. 18D) and provides a description and arecommended action for each condition. An X represents a neutralindicator. TABLE X AI Top Indicator Conditions Pass Fault Active LockDescription Action On Off On Off Module is operating normally. No actionis required. On Off Off Off Possible conditions: Application program hasnot been If module is the hot spare, loaded into the MP. no action isrequired. Application program has been If module is active, replaceloaded into the MP, but has not module. been started up. Module has justbeen installed and is currently running start-up diagnostics. The othermodule is active. Off On X Off Possible conditions: Module may havefailed. See mode indicator status for power-up states. Module may be inthe process of If module's PASS indicator power-up self-test. does notgo on within five minutes, replace module. Module has detected a fault.Module is operational, but should be replaced X X X On Module isunlocked from the Lock module. baseplate. On On X X Indicators/signalcircuitry on the Replace module. module are malfunctioning

The following table XI lists the conditions that can be represented bythe Field Power indicator. TABLE XI Field Power Indicator ConditionsField Power Description Action On Field power from one or To isolate themissing power more of the redundant source, use the Development sourcesis missing. System computer Diagnostic Panel. To determine the output'sactual state, use a Voltmeter, then correct the problem in the externalcircuit. If these steps do not solve the problem, replace module OffField power is No action is required. operating normally.

The table XII below lists the conditions represented by the topindicators on the Relay Output RO front panel (see Figure E) andprovides a description and a recommended action for each condition. An Xrepresents a neutral indicator. TABLE XII Pass Fault Active LockDescription Action On Off On Off Module is operating normally. No actionis required. On Off Off Off Possible conditions: Application program hasnot been If module is the hot spare, loaded into the MP. no action isrequired. Application program has been If module is active, replaceloaded into the MP, but has not module. been started up. Module has justbeen installed and is currently running start-up diagnostics. The othermodule is active. Off On X Off Possible conditions: Module may havefailed. See mode indicator status for power-up states. Module may be inthe process of If module's PASS indicator power-up self-test. does notgo on within five minutes, replace module. Module has detected a fault.Module is operational, but should be replaced X X X On Module isunlocked from the Lock module. baseplate. On On X X Indicators/signalcircuitry on the Replace module. module are malfunctioning

The following table XIII lists the possible conditions that can berepresented by a point indicator. TABLE XIII Point (1-32) Description OnField circuit is energized. Off Field circuit is not energized.

Indicators for other input/output modules are similarly configured asnecessary.

FIG. 17 shows the manner in which the cover 20 interconnects with thebase. The cover 20 includes a cover interlock 67 which mates with acorresponding base 21 interlock 68. The cover and the base 21 are thenscrewed together after insertion of the circuit board sandwich 7 shownin FIG. 16 and the thermal conductive material inside the housingutilizing screws 73 in cover screw holes 69 a and 69 b and base screwholes 70 a and 70 b as shown in FIG. 13. Although any fastening methodmay be used.

Alignment of the housing 29 on insertion can be difficult. Accordinglythe single jack screw 50 as shown in FIG. 13 is utilized which has ascrew thread 51 at one end for engaging the base plate 49 for mounting.The single jack screw 50 is centered in the housing 29 and is mountedthrough the jack screw hole 74. The use of a single jack screw 50 seatsthe module upon entry and unseats the module on exit, that is, onengagement and disengagement from the connectors. A snap ring 52 isattached to one end of the jack screw 50 and engages an annular recess62 on the jack screw 50 to hold the jack screw 50 in position within thehousing at the base 44, a handle 53 holds the jack screw in place at theface plate 39. This permits the jack screw 50 to pull the module out ofits connectors on unscrewing the jack screw 50 which remains mounted tothe housing 29. The handle 53 of the jack screw 50 pulls the housing 29into its seat on screwing in of the jack screw 50. This configurationallows ease of insertion and removal of the housing 29, and provides asafety factor in that the housing 29 is first grounded on mounting priorto power being applied.

The jack screw 50 has an LED detector notch 63 therein which allows thebeam from a detector LED, which may be mounted on either circuit boardin the housing, but preferably on the power board 56, such that thelight beam from the LED is to be intercepted when the jack screw 50 isfully seated. If the jack screw 50 is not fully seated, the LED beam isinterrupted and the system determines that the module is not fully orproperly seated.

When “removed status” is detected, the SX 15′ evaluates the applicationprogram and if the retentive data is invalid, re-education (reload) fromanother MP 15 with a valid application program occurs. If no other MP 15has a valid application program, the SX 15′ waits in the Stop mode for anew application program to be loaded, the MP 15 is commanded to theProgram Run or Remote state, and commanded to download and run.

The “Module Lock Detector” indicates the MP/IOP module is seated andlocked into its base-plate 65 a as shown in FIGS. 5A and 5B. This statusis readable by both MPC860s and reflected in the module status message.The Lock detector is implemented using a reflective typeopto-interrupter now shown which detects the position of the slot on thejack screw 50. The locked state is indicated by the opto-interrupter inthe ON (low-conducting) state, i.e. the opto-interrupter signal isblocked by the jack screw 50. The opto-interrupter is diagnosable underfirmware control which allows at least 1 ms for the opto-interrupter tochange state. The UNLOCK led is forced off in hardware by a lockdetector diagnostic bit.

Hot-insertion of the MP/IOP 1 or any other modules into the base-plateis provided using the detectable keyed insertion jack screw 50 to insureproper installation orientation and correct module type.

Each housing 29 is mounted on a base-plate 65 as discussed before asshown in FIGS. 5A and 5B. Each base plate 65 may support more than onemodule. The base plates 65 are mounted to rails 66 and multiple baseplates 65 may be mounted in a single system. FIGS. 5A and 5B showmounting for both a minimum system and a large system.

FIGS. 19A and 19B illustrate the mounting of the baseplate for the mainprocessor module MP/IOP module 1 showing its baseplate 65 a mounted tothe rail and its interconnections. FIGS. 20A and 20B illustrate themounting of the Digital In module showing its baseplate 65 b mounted tothe rail and its interconnections. FIGS. 21A and 21B illustrate themounting for the Digital Out module showing its baseplate 65 c mountedto the rail and its interconnections. FIGS. 22A and 22B illustrate themounting for the Analog In showing its baseplate 65 d mounted to therail and its interconnections. FIGS. 23A and 23B illustrate the mountingfor the Relay module showing its baseplate 65 e mounted to the rail andits interconnections.

Rail 64 mounted base-plate assemblies permit stacking of several modulesas shown in FIGS. 5A and 5B. Each module is housed in a unique housing29 as described above which provides extended make-first/break-lastsafety and signal ground pins 47. Also, a safety ground connection tothe rail is supplied by the base-plate assembly.

Redundant 24 VDC power supplies are provided to provide a back up in thecase of power supply failure. In the preferred embodiment, the MP/IOP 1is based on the Motorola QUICC microprocessor, the MPC860, as notedabove, and includes support for at least 32M bytes of application memory(DRAM). Error detection via parity, background diagnostic, and voting,correction via leg re-education are also provided as is hereinafterdescribed. TABLE XIV MP/IOP Base-Plate Requirements ConnectorRequirements Qty Connector Function 1 6 pin Terminal block VSP1, VSP2 24v logic power and PE 1 4 pin Terminal block Redundant Alarms 4 Fuseholders VSP1, VSP2 and Redundant Alarms 3 Address Plug Node Address 3DB9p RS232/RS485 Modbus 3 DB9p Reserved - not installed 2 96 pin DINIO/LCM Module power and LIO bus 2 96 pin DIN LCM Left & Right 3 ShieldedRJ45 802.3 10BaseT connector 3 RJ12 Debug - Diag Read port 3 96 pin DINController board 3 48 pin DIN - E Power Interface board 12 Extended PinFE and PE. (Logic and Chassis ground)

The base-plate contains 3 address plugs (one multi-part address plugconnector), one per leg. Base-plate Address plugs are visible withmodules and cables installed. The Node set via the Address plugs on theMP/IOP base-plate. MP/LIOC address plugs are readable by both MP 15 andIOP 17 CPUs. The same Address plugs are used by the expansion IOP 17 todefine the “String number” to support multiple IOP s+I/O module stringsfrom a TMR MP/LIOC.

Synchronization System Synchronized Timing Adjustment

A synchronization system subsystem (TMR Time) is the basis for MP 15scan synchronization and rendezvous. The subsystem consists ofintegrated hardware and firmware components, which allows the MPs 15 tobe loosely coupled in hardware, i.e. run independent of scan, and stillmaintain very tight leg-to-leg synchronization, i.e., from scan to scan+/−50 us. Tight synchronization is required to minimize the amount oftime that the MP/IOP modules 1 wait to synchronize a Channel 11rendezvous. Leg-to-leg (channel to channel) isolation is designed toprotection against ground shorts or neighboring legs at 36 volts withoutcausing permanent damage or effecting the operation of the leg.

Each MP/IOP module 1 rendezvous using synchronization system based uponeach MPs 15 own internal time base, not a common external event orclock. synchronization system is used to implement Channel 11Synchronization Rendezvous, Leg time synchronization

With reference to FIG. 24 registers are used for time synchronization inan FPGA 77. A 24 bit Timer register 96 counts 1μ ticks based the MPC86050 MHz 25 ppm clock 51. The SX 15′ may read the Timer register 96 at anytime to obtain relative time. The SX 15′ uses relative time of themidpoint processor to determine when to perform its next Channel 11rendezvous for voting based on a programmed delta time parameter. ForMP-to-MP time synchronization, a Time compare register 98 generates asynchronization pulse which is applied to the up and downstream MP 15sections through amplifiers 54 and 55 respectively when the Timerregister 96 matches the Time register 97 in the FPGA. The SX 15′calculates and loads the Time register 97. Four capture registers, tworegisters 99 and 100 for upstream and downstream captured the timerregister, and two registers 103 and 104 for attenuated loop-back captureare readable by SX 15′. The capture registers capture the value of theTimer register when a synchronization pulse is received. The SX 15′ usesthe delta between the capture registers and its own time to make smalladjustments to its Timer register 96 time base and to detect faults.

The synchronization system hardware is optimized to minimize the realtime (instantaneous) work required by SX 15′. Synchronization systemservicing does not require MPC860 interrupts. Synchronization system isimplemented in a FPGA 77 which is accessible by the SX 15′.

An adjustment trim register 99 is provide to compensate for time basecrystal oscillator drift. The adjustment trim register 99 adjusts thetime base by dropping or adding 40 Ns to the time base clock, 1 us clockevery M us based on adjustment counter 63, where M is programmable from40.96 us to 0.66666496 seconds in 40.96 us increments.

The synchronization system architecture is scaleable to include at leastone additional register not shown, to provide for a Hot spared MP/IOPmodule 1

The synchronization system time synchronization accuracy is selected tominimize Channel 11 rendezvous window to provide synchronizationresolution required for 1 ms sequence of events timing, and to providetime base fault detection and isolation between MP-15 legs.

The synchronization system does not drift more that +/−50 us over a, 1second period. To provide a 10× margin, the minimum synchronizationsystem accuracy is +/−50 us/10 s or +/−5 ppm. The synchronization systemtimer base is accurate to +/−25 ppm (drift +/−25 us per second),therefore the SX 15′ trims (adjust) this time base 105 to provide therequired accuracy between MPs 15.

The synchronization system and the SX 15′ synchronizes the MP 15 to anaccuracy of +/−50 us. This sets the normal Channel 11 rendezvous windowto 100 us. The time base 105 is derived from the MP 15 MPC860 50 Mhz 25ppm crystal oscillator, divided by 4 for time base adjustments, anddivided by 12.5 (12 then 13 then 12 . . . ) for the Timer register 97.Given an accuracy of +/−50 us, the time resolution of thesynchronization system timer and capture registers is approximately anorder of magnitude better, or: +/−5 u. Assuming the longest System scanis 500 ms, the timer should roll twice per scan so that SX can detectregister roll-over and maintain the high order timer bits in systemmemory, therefor the timer must not roll twice per scan. 500 ms/1 us<2¹⁹or 19-bits. In addition, to permit the timer to be diagnosed, the timershould roll over at least once per 10 minutes (diagnose timerequirement). 600 s/1 us>2²⁹ or 29 bits. A timer length of 24 bitssatisfies both requirements and minimizes FPGA 77 hardware. Roll overoccurs every 16.77721594 seconds. Capture registers and Time registersare 24 bits and the timer roll flag sets when the timer rolls over tozero.

Referring to FIG. 24 the synchronization system FPGA 77 includes all ofthe synchronization system registers which are memory mapped andincludes a method illustrated in FIG. 25 for adjustment of each MP'ssynchronization system timer time base. This is important since the MP15 time synchronization pulses may arrive at any time relative to anMP's timer's value. The timer FPGA 77 method generates a pulse when theTimer register 96 matches the Time register 97. The capture registerslatch the contents of the Timer (double synchronized to the time baseclock/2 and latched on the next microsecond) on the rising edge of eachsynchronization pulse. The Synchronization pulses are at least 3 us wideto allow the MP-MPC860 time to poll for the presence of the pulsesduring power up diagnostics and SX 15′ startup.

Referring to FIG. 25, the operation of the time synchronization is shownby way of example. Processor A initiates a synchronization pulse 108,processor B initiates a synchronization pulse 109 ten microseconds fromthe leading edge of the A pulse 108. Processor C initiates asynchronization pulse 110 twenty microseconds from the leading edge ofthe B 109 pulse. Assuming, the clocks of each processor are running at adifferent count, e.g. A at 500, B at 100, C at 1000, the each processorwould synchronize the clocks as follows:

MY (A) captures its clock 111 a at 500 on generation of itssynchronization pulse. On receipt of the downstream MY (B)synchronization pulse, MY (A) captures its clock 111 c at 510 On receiptof the upstream MY (C) synchronization pulse, MY (A) captures its clock111 b at 530.

On receipt of the upstream MY (A) synchronization pulse, MY (B) capturesits clock 112 b at 90. MY (B) captures its clock 112 a at 100 ongeneration of its synchronization pulse. On receipt of the downstream MY(C) synchronization pulse, MY (B) captures its clock at 112 c at 120

On receipt of the upstream MY (B) synchronization pulse, MY (C) capturesits clock 113 b at 970. MY (C) captures its clock 113 a at 1000 ongeneration of its synchronization pulse. On receipt of the downstream MY(A) synchronization pulse, MY (C) captures its clock 113 c at 970.

By examining the capture times each processor determines which processorwas midpoint. That is in between the pulses of the other processors.Accordingly, (A) picks a count of 510 which adds 10 us to its clock and(C) picks a count of 980 which subtracts 20 us from its clock therebysynchronizing the processors.

The synchronization system Timer register 96 includes STOP and CLEARcontrols. SX 15′ polls for synchronization pulses from the other MPmodules 1 (if any) before generating an external synchronization pulse(T). Alternatively, the SX 15′ may clear and stop the Timer register 96and wait for a synchronization pulse. On receipt of the synchronizationpulse, the SX 15′ uses the adjust registers to acquire synchronization.The following steps occur in each scan time sequence;

to, step 601

-   -   1) SX 15′ reads the synchronization system capture registers and        loop-back status.    -   2) SX 15′ checks for roll over and increment, the high order        time bits kept in memory.    -   3) SX 15′ selects an MP leg (mid-point) to be used for trim        calculations.    -   4) SX calculates a real time value for the next synchronization        pulse and load time into synchronization system Time register.

t1-t3, step 602

-   -   The synchronization system capture registers 99, 100, 101, 102,        103 and 104 capture the synchronization system timer register 96        value to the nearest 1 us when an external synchronization pulse        is received. Previous values are over-written.

t2, step 603

-   -   synchronization system generates a synchronization pulse when        the Timer register 96 matches the Timer 97.

t4, step 604

-   -   Returns to t0, for next scan.

Note: t0-t4 are arbitrary time markers use to illustrate thesynchronization system sequence.

The FPGA 77 contains and decodes the following registers set forth inTable XV. TABLE XV Address CS6 + 80 Hex Register Format Addr MSBRegister LSB 0x80 Roll Stop TT_INT T register (Time) 24 b - r/w 0x84Roll Stop TT_INT T counter (Timer) - Free running 24 b - r/o 0x88 RollStop TT_COF Upstream loop-back capture 24 b - r/o 0x8C Roll Stop TT_COFDownstream loop-back capture 24 b - r/o 0x90 Roll Stop UP_COF Upstreamcapture 24 b - r/o 0x94 Roll Stop DN_COF Downstream capture 24 b - r/o0x98 Roll Stop 0 not used 0x9C Roll Stop 0 not used 0xA0 Adj Enable NReg M Reg Control register - 16 b -r/w 0xA4 0 Status clear bits - 16 b-w/o

The T register (Time register) determines when the synchronizationsystem Synchronization Pulse output signal (TTS is generated. The TTSpulse is generated for 3 us when the T register=T counter evaluatestrue.

The T counter (Timer register) counts 1 us time base clocks. The Tcounter is free running. The Roll bit indicates when the T counter hasrolled past the 24 bit Capture and Time register boundary and thesoftware of the MP 15 accounts for this when capturing time.

Referring again to FIG. 24 and Table XV, the upstream attenuatedloop-back capture register 99 latches the value of the T counter 96 whenthe Upstream attenuated loop-back detects a output synchronization pulse(TTS). The T counter Roll and Stop bits are also captured. This registerdetects faults in the “MY to Upstream” Synchronization pulse driver andbackplane pins. The upstream loop-back capture register 99 is unknownuntil the first TTS pulse is detected. Roll and Stop indicate the stateof the ROLL and stop flags when the capture occurred. TT_COF (captureoverflow) indicates that TT_INT was already set when the captureoccurred. The TT_COF bit will not clear until the TT_INT bit is clearedand the next TSO capture occurs.

A Downstream attenuated loop-back capture register 100 latches the valueof the T counter 96 when the Downstream attenuated loop-back detects aoutput synchronization pulse (TTS). The T counter 87 Roll and Stop bitsare also captured. This register detects faults in the “MY toDownstream” Synchronization pulse driver and backplane pins.

This Downstream Loop-back register 100 is unknown until the first TTSpulse is detected. Roll and stop indicate the state of the ROLL and stopflags when the capture occurred. TT_COF (capture overflow) indicatesthat TT_INT was already set when the capture occurred. The TT_COF bitwill not clear until the TT_INT bit is cleared and the next TSO captureoccurs.

An Upstream capture register 103 latches the value of the T counter 96when the Upstream Synchronization pulse is detected. The T counter Rolland Stop bits are also captured. The Upstream Capture register 103 isunknown until the first Upstream Synchronization pulse (T) is detectedor until the UP_LBEN (Upstream loop-back enable) bit is set in thecontrol register and a synchronization system Synchronization Pulse(TTS) is generated. Roll and stop indicate the state of the ROLL andstop flags when the capture occurred. UP_COF (capture overflow)indicates that UP_CF was already set when the capture occurred. TheUP_COF bit will not clear until the UP_CF bit is cleared and the nextUP_S capture occurs. (See TT control register)

The Downstream capture register 104 latches the value of the T counterwhen the Downstream Synchronization pulse is detected. The T counter 96Roll and Stop bits are also captured. The Downstream Capture register104 is unknown until the first Downstream Synchronization pulse isdetected or until the DN_LBEN (downstream loop-back enable) bit is setin the control register and a synchronization system SynchronizationPulse is generated. Roll and stop indicate the state of the ROLL andstop flags when the capture occurred. DN_COF (capture overflow)indicates that DN_CF was already set when the capture occurred. TheDN_COF bit will not clear until the DN_CF bit is cleared and the nextDN_S capture occurs.

The control register 97 provides miscellaneous functional and diagnosticcontrol of the synchronization system subsystem.

Channel Data Transfer and Voting

There are three MP/IOP modules 1 in a preferred system of the presentinvention as noted above. As shown in FIGS. 10A and 10B the three MP/IOPmodules communicate with each other via an inter-MP bus or channel. 11.The Channel 11 is a three channel parallel to serial/serial to parallelcommunications interface with a DMA controller, hardware loop-back faultdetection, CRC checking and MP to MP electrical isolation is a highspeed communication path between the three MPs 15 primarily used forvoting. The three MPs 15 a, 15 b and 15 c are time synchronized witheach other by a synchronization system.

In operation as shown in FIG. 2 each leg (Channel A, B, C) of the systemcontroller is controlled by a separate MP/IOP module 1. Each MP/IOPmodule 1 operates in parallel with the other two MP/IOP modules 1, as amember of a triad. Each IOP 17 scans each LIO module 2 installed in thesystem of the present invention via the RS485 2 Mb LIO bus 13 at apredetermined time interval (set by the initial programming). As eachmodule is scanned, new input data is transmitted by the IOP 17 to MP 15via the shared memory module 16 located on the MP/IOP printed circuitboard. The SX 15′ assembles the input data and stores the input data inan input table in its memory 16 for application program evaluation.

Channel Voting

Prior to application program evaluation, the input table in memory 16 iscompared with the input tables in memory 16 on the other MPs 15 via thechannel. 11.

The input data in each MP 15 is transferred to the other MP 15 modulesin the system and “voted” by the SX 15′ firmware. If a disagreement isdiscovered, the value found in two out of three tables prevails, and thethird table is corrected accordingly. Each MP 15 maintains history datafor corrections and faults. Any continuing disparity with the same leg,register or the like is recorded for future handling at a predeterminedoccasion by the SX 15′ Fault Analyzer routines.

The SX votes inputs before passing them to the application program toinsure that the inputs are correct. Voting will be based on a majorityvote on comparison and the defaulting MP/IOP module 1 data will becorrected. The SX 15′ votes the inputs in accordance with the followingTable XVI dependent on the number of MP/IOP module 1 processors in thesystem and whether the data is analog (a number) or discrete (on oroff). TABLE XVI Voting Mode Comparison Operating Number of DiscreteAnalog Input Mode Legs Enabled Voting Voting TMR 3 2-out-of-3 Mid ValueDuplex 2 2-out-of-2 Average Single 1 1-out-of-1 1-out-of-1 Safe 0De-energized NA

Accordingly, when in TMR mode, i.e. three processors enabled, Digital orDiscrete voting is conducted on 2 out of 3 matching. For Analog votingthe Midpoint value is selected.

When in Duplex Mode, i.e. two processors enabled, Digital or Discretevoting is concluded on a 2 out of 2 matching. For Analog voting theAverage value is selected. For single processor voting the valuepresented is the value selected for either Discrete or Analog voting.

After such comparison is made the selected value is restored to anytable having different values.

In addition to Input comparisons, the SX 15′ will also compare theoutputs every scan. It will be considered a safety fault, if a MP 15output data does not compare with the other MP's output data inaccordance with Table XVI. Internal variables will also be compared on aperiodic basis as is predetermined by the SX 15′ code which can testevery scan. The application program code will also be compared on aperiodic basis as is predetermined by the SX 15′ code which can also beevery scan. Any comparison failure is considered a safety fault.

After the channel 11 transfer and input data voting has corrected theinput values, the values are evaluated by the application program. TheDevelopment developed application program is executed by the SX 15′ inparallel on each MP 15 using an MPC860 microprocessor which is asuitable CPU for the MP 15. The application program generates a set ofcontrol system output values based upon the control system input values,according to the rules built in to the program by a Control Engineer fora particular installation. The MP 15 transmits the output values to theIOP 17 via shared memory 16 over interface 18. The MP 15 also votes thecontrol system output values via channel. 11 to detect faults. The IOP17 separates the output data corresponding to individual LIO Modules 2in the system. Output data for each LIO module 2 is transmitted via theLIO bus 13 to the output modules.

Channel Data Transfer

At predetermined times each MP 15 rendezvous with the other activemembers of the triad via the synchronization system and compares andvotes all application program input data. During this comparison theactual data is voted a using a majority override mechanism as notedabove and all discrepancies corrected where appropriate. Each MP 15 istransferred a copy of the other's data to compare against and correctit's own copy as required over the channel 11. Along with the inputdata, portions of the MP 15 memory and hardware status shall transferredto the other MPs 15 via Channel 11 and compared by firmware.Discrepancies constitute a fault.

Voting is performed by SX instructions. The Channel 11 is similar to ageneric multi-channel communications controller using buffer descriptorsexcept that Channel 11 is optimized for TMR SX 15′ operation andincludes, real time fault detection and fault location of most faultsvia attenuated transmit loop-backs, no single Channel 11 failuredisables more than one MP 15, no physical Channel 11 interface signalinterfaces with more than one other MN 15. (Physical interfaces arepoint-to-point).

A typical channel 11 transfer used for voting purposes consists of thefollowing steps:

Rendezvous (synchronization system) step 701

Transferring of data to be voted (Channel 11) step 702

Analyzing transfer results (SX), CRC, status, and the like, step 703

Transferring 1st results data resulting from analyzing transfer resultsto other MW Modules 1 (Channel 11) step 704

Accumulating transfer results (SX), received from other MP Modules, step705

Transferring 2nd results data indicating voting mode to be taken(Channel 11) step 706

Analyzing and Voting the data, step 707

Voting Mode Selection

A combination of firmware algorithms (lookup table) and Channel 11attenuated loop-back information permits the MPs 15 in the triad todetect, locate and contain any single leg Channel 11 faults to thefaulted leg. In addition, the fault status information also allows thenon-faulted MPs 15 in the triad to unanimously agree on the votingmechanism (TMR, Dual or Single). It is important that all MPs 15 voteusing the same voting mode, since voting TMR will result in different(although correct) analog values V/S voting in Dual mode. To insure thatall MPs participating in the vote arrive at the same voting mode in thepresence of a Channel 11 fault, the following Channel 11 resultaccumulation tables is used. TABLE XVII Channel 11 transfer accumulatedresults table Channel 11 Transfer Path fault information accumulated perMP leg (True/False Boolean data) After Channel 11 Mum Mdm Mlmu Mlmd datatransfer After 1st result Umu Udu Ulum Ulud Dmd Dud Dldm Dlum transferAfter 2nd -result Dumu DUdu DUlum Dulud UDmd UDud UDldm UDldu transfer

In order for voting to accurately determine a result the following rulesare set regarding the Channel 11 results:

True=Data Transfer Worked, good CRC and good sequence number.

False=Data Transfer failed/missing or bad CRC or bad sequence number.

All transfers are “written”. I.E. One leg can not pretend to be another.

Only one leg faulted at a time.

A false value can not be made true by passing it through the bad leg.False values stay false.

A true value may be made false (or stay true) by passing it through thebad leg. I.E. True values may go false when passed through the bad leg.

A true value passed through a good leg stays true.

Loop-back status always correctly detects the fault location. TABLEXVIII Path Faults Paths and possible Single faults locations TransmitFault Receive Path at: Fault at: mu M U md M D um U M ud U D dm D M du DU

TABLE XIX Vote selection mode truth table TMRvote RMum & RMdm & (Rumu |RDUmu) & (RUdu | RDUdu) & (RDmd | UDmd) (RDud | RUDud) Fault Voter PathFault At: Solution Boolean Equation Single leg faults resulting in Dualvoting: DUALvote MvUD_fMmu M UD <= !MRUmu & !MDRUmu & (RMRUdu|MDRUdu) &(MRDud|MURDud) & !Tmmu MvMD_fUmu U MD <= RMdm & !MRUmu & !MDRUmu &(MRDmd|MURDmd) & TMmu MvUD_fMmd M UD <= !MRDmd & !MURDmd &(MRUdu|MDRUdu) & (MRDud|MURDud) & !TMmd MvMU_fRDmd D MU <= RMum & !MRDmd& !MURDmd & (MRUmu|MDRUmu) & TMmd MvMD_fUum U MD <= !RMum & RMdm &(MRDmd|MURDmd) & !MTUum & !MDTUum MvUD_fMum M UD <= !RMum &(MRUdu|MDRUdu) & (MRDud|RMURDud) & (RMTUum|MDTUum) MvMD_fUud U MD <=RMdm & (MRDmd|MURDmd) & !MRDud & !RMURDud & !RMTUud & !MDTUud MvMU_fDudD MU <= RMum & (MRUmu|MDRUmu) & !MRDud & !MURDud & (MTUud|MDTUud)MvMU_fDdm D MU <= RMum & !RMdm & (MRUmu|MDRUmu) & !MTDdm & !MUTDdmMvUD_fMdm M UD <= !RMdm & (MRUdu|MDRUdu) & (MRDud|MURDud) &(MTDdm|MUTDdm) MvMU_fDdu D MU <= RMum & (MRUmu|MDRUmu) & !MRUdu &!MDRUdu & !MTDdu & !MUTDdu MvMD_fUdu U MD <= RMdm & (MRDmd|MURDmd) &!MRUdu & !MDRUdu & (MTDdu|MUTDdu) Multiple faults resulting in Singlemode voting: SINGLEvoteEnd of scan copy: TMRmode <= TMRvote, DUALmode <= DUALvoteExample line 2 of Path fault: MvMD_fUmu

My vote is MY and Downstream, fault located at Upstreams MY to Upstreaminterface: I.E., Upstream Receiver is bad

The equation reads:

-   RMdm->I received good data from downstream.-   !MRUmu->Upstream reports he did not receive my data.-   !MDRUmu->Downstream reports that Upstream reports he did not receive    my data.-   MRDmd->Downstream reports he did receive-my data.-   MURDmd->Upstream reports that Downstream he did receive my data.-   TMmu->My upstream Transmit is good.    Note: Voting UD cases are for fault diagnosis only, M fails in this    case and does not actually vote.    Redundant written terms has not been reduced out.

Abbreviations

Note: These terms are concatenated to form first and second hand statusinformation used to determine the voting mode.

M=my view

U=Up's view

D=Down's view

v=vote is . . .

f=fault located at . . . .

Operators: !=not, |=logical “OR”, & =Logical “AND”

RM=my view of another legs data packet status through My receiver

RU=Ups view of another legs data packet status through UPs receiver

RD=Downs view of another legs data packet status through DNs receiver

TM=my view of my loop-back status

TU Ups view of Ups loop-back status

TD=Downs view of Downs loop-back status

um=result of transfer from path Up to MY

dm=result of transfer from path Dn to MY

lmu=result of my hardware loop-back from Up to MY path

lmd=result of my hardware loop-back from Dn to MY path

mu=result of transfer from path MY to Up

du=result of transfer from path Dn to Up

lum=result of Up hardware loop-back from Up to MY path

lud=result of Up hardware loop-back from Up to Dn path

ud=result of transfer from path Up to Dn

md=result of transfer from path MY to Dn

Idm=result of Dn hardware loop-back from Dn to MY path

Idu=result of Dn hardware loop-back from Dn to Up path

Skip_OK=Ok to skip a scan. This term prevents the MP from skippingconsecutive scans or too many scans per TBD time period.

TMRmode=Last vote was TMRvote. Used to determine.

DUALmode=Last vote was DUALvote. Used to determine.

SINGLEmode=Last vote was Single vote.

TMRvote=Voting TMR this scan.

DUALvote=Voting DUAL this scan.

SINGLEvote=Voting Single this scan.

The method of voting mode selection includes the following steps. The SXsystem checks the lookup truth table, and the capture register values,step 801. The system then checks for any faults or any processor leg,step 802. If no faults are detected, then the system enters TMR votingmode. If a fault is discovered, step 802, the system determines if morethan one processor is faulted, step 803. If so, the system continues insingle processor voting mode, step 804. If all of the processors arefaulted, the system halts.

A hardware clock calendar circuit is used to maintain the time and dateduring the MP power-off state and for OSE. The synchronization systemFPGA firmware based clock calendar routines are used to maintain thetime and date during the MP power-on state. This time is voted betweenthe MPs.

Attenuated Hardware Communication Interface Loop-Back

TriBus channel transmit data loop-back receiver-checkers independentlycheck the upstream and downstream transmit data drivers. As shown inFIG. 24 Loop-back registers 99 and 100 are connected through thebase-plate so that the transmit data driver base-plate connectors pinswill also be diagnosed. The loop-back receivers are slightly attenuatedwith respect the MPs upstream and downstream receivers so that a weaktransmitter will be detected by the loop-back receiver before it isdetected by the up or downstream receiver. This feature providesextremely accurate fault identification and location.

When data signals are transmitted to adjacent processors on the variousprocessor legs as shown in FIGS. 11A and 11B, each processor 90, 91 and92 has an upstream and downstream loop back path, 90 b, 90 d, 91 b, 91d, 92 b and 92 d, respectively. The loop back capture registers capturethe level of the signal. The signals are attenuated to switch the signalvalue received by the other upstream and downstream processors. Sincethe loop-back signal is first received by the transmitting processor,the expected return value can be evaluated.

Terms and Acronyms Used in this Specification

Channel (Also know as Leg) An independent I/O Input->MP->I/O Output path

-   LCM Local Communication Module-   LCM Bus Bus between MP and Local Communication module-   LIO or IO BusInterface between IOP s and IO modules-   IOP System Input Output Processor-   IOP Bus Bus between MP/IOP and expansion IOP s-   LIOX or IOX System Input/Output Executive firmware-   MP System Main Processor-   LRXM or RXM System Remote Extender Module-   LSX or SX Executive firmware System of the present invention-   MAU Media Adapter Unit—for 803.2 networks-   TMR Triple Modular Redundant-   TRICON TRICONEX Fault Tolerant PLC-   channel. MP inter-processor communications bus-   TriLan Triplicated Peer to Peer Bus-   Trinode A System MP on TriLan.-   synchronization system MP Time synchronization subsystem-   DMA Direct memory access-   TCP/IP Transmission Control Protocol/Internet Protocol-   PC Personal computer-   DCS Host Distributed processor control systems host LAN Local area    network    Legs Channel

LMP/LIOP or MN/IOP Main processor/input output module

-   Modbus A Modicon protocol bus-   LCB Local communications bus-   Control Program Program developed by user for control of industrial    environment-   FRS Field replaceable subsystem

While specific embodiments of this invention has been described above,those skilled in the art will readily appreciate that many modificationsare possible in the specific embodiment, without materially departingfrom the novel teachings and advantages of this invention. Accordingly,all such modifications are intended to be included within the scope ofthis invention.

1. A system for validating communications between a plurality ofprocessors comprising: a plurality of loop back paths, wherein each ofthe loop back paths is coupled to a corresponding one of the pluralityof processors, wherein each loop back path includes an attenuationelement of a predetermined value, said attenuation elements configuredto attenuate a one of a plurality of signals transmitted from each ofthe corresponding one of the plurality of processors by a predeterminedamount so as to generate a plurality of loop back signals; a pluralityof signal transmission paths, wherein each of the signal transmissionpaths is configured to carry a corresponding one of the plurality ofsignals from one of the plurality of processors to another of theplurality of processors; a plurality of data checkers, wherein each ofthe data checkers is configured to compare one of the plurality of loopback signals to a corresponding one of the plurality of transmissionsignals so as to enable the validity of each of the plurality of signalsto be assessed.
 2. The system of claim 1 including: at least oneinput/output module configured to send control system information toeach of the plurality of processors.
 3. The control system of claim 1,including: a plurality of memory modules, wherein each of the pluralityof memory modules is coupled to a corresponding one of the plurality ofloop back paths, wherein each of the memory modules is configured tostore information relative to a corresponding one of the plurality ofloop back signals.
 4. The control system of claim 3 wherein one of theplurality of memory modules and one of the plurality of data checkers isintegrated with a corresponding one of the plurality of processors. 5.The control system of claim 1 wherein said attenuation element comprisesa resistive element selected to provide a predefined signal level marginbetween said signal transmission path and said loop back signal path. 6.The control system of claim 5 wherein said margin is approximately 30millivolts.
 7. The control system of claim 5 wherein said resistiveelement has a value of approximately 250 ohms.
 8. A control system forexecuting a common application program comprising: three processormodules configured to execute the common application program in asubstantially simultaneous fashion, at least one field input/outputmodule disposed to receive communicating with the three processormodules; and an attenuated feed back system for determining faults incommunications between the three processor modules.
 9. The controlsystem of claim 8, wherein a first of the three processor modules isconfigured to transmit a signal to a second of the three processormodules, and wherein the attenuated feed-back system includes a loopback path coupled to the first of the three processor modules, whereinthe loop back path includes a first attenuation element having apredefined attenuation value, said first attenuation element configuredto attenuate the signal by a predefined amount so as to generate a firstattenuated signal, wherein the first of the three processor modules isconfigured to compare information in the first attenuated signal andinformation in the signal so as to determine whether there is a fault incommunications between the first and the second of the three processormodules.
 10. The control system of claim 9, wherein the first of thethree processors is configured to transmit the signal to a third of thethree processor modules, and wherein the attenuated feed back systemincludes a second loop back path coupled to the first of the threeprocessor modules, wherein the second loop back path includes a secondattenuation element having a predefined attenuation value, said secondattenuation element configured to attenuate the signal by a predefinedamount so as to generate a second attenuated signal, wherein the firstof the three processor modules is configured to compare information inthe second attenuated signal and information in the signal so as todetermine whether there is a fault in communications between the firstand the third of the of the three processor modules.
 11. The controlsystem of claim 9, wherein the loop back path is coupled to a connectorpin external to the first processor module so as to enable the connectorpin to be diagnosed.
 12. The control system of claim 9, wherein thefirst of the three processor modules includes: a capture registerconfigured to capture the attenuated signal and a data checkerconfigured to compare information in the signal with information in theattenuated signal.
 13. The control system of claim 9, wherein the firstattenuation element is a resistive element, the resistive value of saidelement selected to provide a predetermined signal level thresholdbetween said signal level and said attenuated signal level.
 14. Thecontrol system of claim 10, wherein the second attenuation element is aresistive element, the resistive value of said element selected toprovide a predetermined signal level threshold between said signal leveland said second attenuated signal level.
 15. A method for determiningthe validity of transmitted information in a multiple processor systemcomprising: transmitting information from a first processor to a secondprocessor; looping back the transmitted information to the firstprocessor through an attenuated loop back path, said attenuated loopback path including an attenuation element having a predefinedattenuation value, so as to generate attenuated loop-back information;comparing, at the first processor, the attenuated loop-back informationwith the information transmitted from the first processor so as todetermine the validity of the information transmitted from the firstprocessor to the second processor.
 16. The method of claim 15 including:capturing the loop-back information; and storing at least one measuredaspect of the loop-back information.
 17. The method of claim 15including storing a result of the comparing in a memory of the firstprocessor.
 18. The method of claim 17 including: identifying a faultwith the first processor when the result indicates a difference in thetransmitted information and the loop-back information.
 19. A method fortransmission validity testing comprising: transmitting information froma transmitting processor to at least one receiving processor;attenuating the information so as to generate attenuated information;comparing, at the transmitting processor, the transmitted informationwith the attenuated information; and generating a fault indication inresponse to the comparing indicating a fault during the transmitting ofthe information.
 20. The method of claim 19, wherein the attenuatingincludes routing the information through an attenuated loop back path tothe transmitting processor, said attenuated loop back path including oneor more attenuation elements selected to have a predeterminedattenuation value.
 21. The method of claim 20 including: capturing theattenuated information; and storing an indication of a level of theattenuated signal.
 22. The method of claim 19 including: transmittingthe information from the transmitting processor to at least tworeceiving processors; wherein the attenuating includes routing theinformation through two attenuated loop back paths to the transmittingprocessor so as to generate two sets of attenuated information; andcomparing the transmitted information with the two sets of attenuatedinformation so as to assess the validity of communications to each ofthe at least two receiving processors.